Skip to content

FINERACT-2480: Remove AppUserClientMapping entity (Phase 1 of self-service removal)#5498

Open
AshharAhmadKhan wants to merge 1 commit intoapache:developfrom
AshharAhmadKhan:FINERACT-2480-remove-selfservice
Open

FINERACT-2480: Remove AppUserClientMapping entity (Phase 1 of self-service removal)#5498
AshharAhmadKhan wants to merge 1 commit intoapache:developfrom
AshharAhmadKhan:FINERACT-2480-remove-selfservice

Conversation

@AshharAhmadKhan
Copy link

Description:
This PR is Phase 1 of removing the insecure self-service feature as requested in FINERACT-2480.

What This PR Does:

  • Removes AppUserClientMapping entity class
  • Removes all references to AppUserClientMapping from AppUser domain class
  • Cleans up client mapping logic from user update methods

Scope:
Phase 1 focuses on entity-level cleanup. Subsequent phases will remove:

  • Phase 2: 18 self-service API controllers (~36 files)
  • Phase 3: Service layer implementations (~40 files)
  • Phase 4: Domain entities and repositories (~25 files)
  • Phase 5: Configuration and security updates (~10 files)

Changes:

  • Deleted: AppUserClientMapping.java (88 lines)
  • Modified: AppUser.java (removed 28 lines)

Testing:
CI will run full test suite to verify no regressions.

Related:

Copy link
Contributor

@IOhacker IOhacker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AshharAhmadKhan I think that it should be a single PR, not in phases.

@AshharAhmadKhan
Copy link
Author

Hi @IOhacker,

Thank you for reviewing this and for the feedback.

I structured the work in phases to keep each change small and easier to review, but I understand the preference for a single PR. I’m happy to align with whatever approach is preferred for the project.

Would you recommend consolidating everything related to FINERACT-2480 into one PR, or keeping it as a single PR with logically separated commits for clarity?

Please let me know the preferred direction and I’ll adjust accordingly.

Thanks again for your guidance.

@IOhacker
Copy link
Contributor

IOhacker commented Feb 15, 2026 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants